home *** CD-ROM | disk | FTP | other *** search
- StarView Archive Text File Snooper V1.0
- Public Domain Software
- (!) 1996 Larry Monte/StarLab Systems Software
- -----------------------------------------------------------------------------
-
- GUARANTEES:
- -----------
- None expressed or implied. If StarView works for
- you...great. If not, feel free to modify the code
- to work on your system.
- -----------------------------------------------------------------------------
-
- What is StarView?:
- ------------------
- StarView is a replacement for your VIEW_FILES command
- in your MAX V3.x file area. It will not only show users
- any text files contained on your system, but will also
- allow them to snoop within archives for text files.
- This is basically a stand-alone version of a feature
- included in StarBar, a lightbar file selecting utility
- released earlier.
- -----------------------------------------------------------------------------
-
- OS/2 Sysops:
- ------------
- Although I haven't heard of any problems with my
- method of external archive snooping, they have
- not been tested extensively on OS/2 systems.
- My main concern is the *.CMD files which are used for
- extracting files from within Archives. Because I have
- no access to an OS/2 system, I could not test these
- files properly.
- I suspect they may work, but if they don't you will
- have to modify the CMD files yourself.
- Further, if you do get them to work (or the originals
- work in the first place) please NetMail me the
- corrections so I can include them in future releases!
-
- -------------==============Basic Setup Instructions=============-------------
-
- NOTE: I suggest everyone to setup StarView by the proceedures outlined below.
- This will make it easier to track down problems if everyone uses the
- program the same way.
-
- 1) Make sure ALL your archivers are somewhere in your DOS path! You need to
- do this for your daily BBS operations, so this _should_ be done already
-
- 2) Make sure you have the MEX_INCLUDE environment set in your autoexec.bat
- file. Your autoexec.bat should have this line:
-
- SET MEX_INCLUDE=c:\max\m
- ^^^^^^^^^
- Should be set to where you keep your *.MH MEX files...
-
- If you don't have this set, add the above line to autoexec.bat and reboot
- your computer!
-
- 3) Unpack the STVIEW10.ZIP archive into a directory off your main BBS dir
- called STARVIEW.
- Here, it's : C:\MAX\STARVIEW
-
- NOTE: If you run StarBar V2.0 on your system, StarView will be quite
- happy sharing that directory!
-
- 4) MOVE (not copy) both STARVIEW.LH and STARVIEW.MH into your ..\m directory.
- Here, it's : C:\MAX\M
- Do not leave a copy of these files in the STARVIEW directory. Make sure
- they are in your ..\m dir ONLY!
-
- 5) Change to your ..\lang directory and load your main <language>.mad file
- (here it's ENGLISH.MAD) into your favorite text editor.
- NOTE: See below on creating other StarView language files for multiple
- language systems.
- At the end of your language file is a section called "User Heap". You
- may see another include file there. Add the following to this section:
-
- ; Include any user heaps here
-
- <Other includes may be defined here>
- #include <../m/starview.lh>
-
- I know there is a USER.LH file where other language files can be defined
- but to keep the least amount of confusion, put the above include line
- in the main <language>.mad file.
-
- 6) Compile your language file:
-
- MAID <Your language here>.mad
-
- 7) Change to your ..\m dir and load STARVIEW.MH into your favorite text
- editor.
- This file contains #defines that _MUST_ be changed before you compile
- and run StarView.
- The StarView.MH file contains all the information about how to change
- the #defines. Just follow those and you should be okay.
-
- 8) After you are finished with the MH file, change to the main StarBar
- directory and compile StarView using:
-
- MEX STARVIEW
-
- 9) Make the following changes to your FILE SECTION in MENUS.CTL:
-
- MEX StarView\StarView Normal "View Text Files"
- ^^^^^^^^
- This replaces the FILE_VIEW entry in the FILE section.
-
- 10) SILT MAX
-
- 11) Run StarView on each node once. You need to do this once so StarView
- can create a node-specific work directory.
- StarView will report there are no Text or Doc files on the first run,
- but will work fine after that.
-
- NOTE: This won't need to be done if you put StarView in the same dir
- as StarBar (if you run StarBar) as you likely did this already
- during the StarBar setup.
-
- That's it. You should have a fully operational copy of StarView working on
- your BBS!
- -----------------------------------------------------------------------------
- ----------------------About the BAT/CMD/GUS/ACL Files------------------------
-
- The distribution setup of StarView uses batch files which do the external
- archive snooping/unpacking. The current *.BAT *.CMD files will work without
- need of 3rd party utils. (You only need the archive programs themselves)
-
- Included are *.GUS(DOS) & *.ACL(OS/2) files. These are included in case you
- wish to use GUS or ACLE to do your archive unpacking. In this case, simply
- rename the *.GUS (for DOS) files to *.BAT or *.ACL (for OS/2) files to *.CMD.
-
- EG:(DOS)
- You have UNPACK.BAT - Delete or rename this
-
- UNPACK.GUS - Copy or rename these to UNPACK.BAT
-
-
- (OS/2)
- You have UNPACK.CMD - Delete or rename this
-
- UNPACK.ACL - Copy or rename these to UNPACK.CMD
-
- NOTE: If you use GUS or ACLE, they _MUST_ be in your main BBS directory, not
- in the StarView dir!! (The *.BAT/*.CMD's should be in your StarView
- directory)
-
- NOTE: Both GUS and ALCE are requestable here @ 1:253/232 as "GUS" and
- "ACLE"
- -----------------------------------------------------------------------------
- -------------------Adding/Modifying StarView Language Files------------------
-
- StarView is capable of using multiple language files. Once you have your
- primary language file using StarView.LH, you can copy this file to another
- name and include it in other language files.
- However, if you don't have translated StarView language files, I recommend
- including StarView.LH in all your "user heaps" in all the language files
- you run.
- If you have translated StarView language files, include the file in the
- appropriate language files.
-
- For instance, say you have a French language file for StarView called
- STARVFR.LH. Put it in your ..\m dir and include this filename in your
- french language "user heap". (Same method as described above)
- MAID the French language file, and try it out. Run StarView under French
- and have a look.
-
-
- Translating:
- ------------
-
- Translating the StarView.LH file shouldn't prove to be too difficult, but
- there are a few things you should keep in mind:
-
- - Take care to preserve the control characters (EG: "\n\n") These are
- line feed characters and may have undesired effects on other strings
- if omitted.
- - Make sure you don't touch the =starview statement which appears
- after the version #define.
- - Enclose all text in quotes (not the colour words)
- - End each string with a ;
-
- -----------------------------------------------------------------------------
- ------------------------------Common Problems--------------------------------
-
- Q: When I compile using "MEX STARVIEW", I get litterally _HUNDREDS_ of errors!
-
- A: You either don't have "SET MEX_INCLUDE" defined in your AUTOEXEC.BAT file
- or you've put the STARVIEW.MH file somewhere MEX can't see it. Make sure
- STARVIEW.MH is in your ..\m directory, and that MEX_INCLUDE is defined
- (see above or MAX.DOC on this) in AUTOEXEC.BAT.
-
-
- Q: MEX tells me that str_* variables aren't defined?
-
- A: You either didn't include STARVIEW.LH in your <language>.mad file, or you
- forgot to MAID it afterwards.
-
-
- Q: StarView always reports "Archive Contains No TXT or DOC files"?
-
- A: Something is wrong with the external archive unpackers. Watch this
- operation carefully and look for DOS error messages, such as "File
- Not Found" or "Directory Doesn't Exist", etc.
- NOTE: You will get this on the first run on each node.
-
-
- Q: When trying to use GUS or ACLE, I get "File Not Found" errors.
-
- A: GUS or ACLE _MUST_ be in your main BBS directory, not the StarView dir.
-
- -----------------------------------------------------------------------------
-
- See Register.Doc for mailing information, if you need to contact me.
-